NetNews Offline 2/NetNews Offline Volume 2.iso/news/comp/sys/amiga/programmer/4897

Text File | 1996-08-05 | 3.7 KB | 79 lines

Path: informatik.tu-muenchen.de!fischerj
From: [e-mail] (Juergen "Rally" Fischer)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: ChangeScreenBuffer()
Date: 6 Mar 1996 13:35:37 GMT
Organization: Technische Universitaet Muenchen, Germany
Distribution: world
Message-ID: <4hk4b9$[e-mail]>
References: <4gl1e7$[e-mail]> <[e-mail]> <4gt3dq$[e-mail]> <[e-mail]> <4het4a$[e-mail]>
NNTP-Posting-Host: hphalle0a.informatik.tu-muenchen.de
To: [e-mail] (Jorge Acereda Macia)
Originator: [e-mail]


In article <4het4a$[e-mail]>, [e-mail] (Jorge Acereda Macia) writes:
|> Organization: Universitat Jaume I. Castell≤ de la Plana. Spain
|> Lines: 50
|> Message-ID: <4het4a$[e-mail]>
|> References: <4gl1e7$[e-mail]> <[e-mail]> <4gt3dq$[e-mail]> <[e-mail]>
|> NNTP-Posting-Host: @rossegat.uji.es
|> X-Newsreader: TIN [version 1.2 PL2]
|>
|> Bjorn Reese ([e-mail]) wrote:
|> > Jorge Acereda Macia ([e-mail]) wrote:
|> > > Bjorn Reese ([e-mail]) wrote:
|>
|> > > There's is another issue... Pressing the depth gadget will freeze
|> > > the game/demo until you release it. Any solution?
|>
|> > None, that I can think of. However, chances are that if the user
|> > is pressing the depth gadget, (s)he's isn't paying attention to
|> > the game/demo and probably wants it to freeze.
|>
|> I mean that if you keep pressing the depth gadget a couple of
|> seconds all the calls to ChangeScreenBuffer() during that time
|> will fail. I've been watching demos and the usual approach is
|> to exit the demo as soon as the user presses the mousebutton,
|> so the problem is solved :-) But for games... It's a different
|> world. Perhaps opening a backdrop window will solve the problem...
|> Will try it tonight.
|>
|> > > > some example in NDK called doublebuffer.c, I believe) However, this
|> > > > can give some strange results under some circumstances, so I prefer
|> > > > WaitTOF().
|> > >
|> > > I had no problem with it... What problems do you refer to?
|>
|> > Let's see if I can remember it...
|>
|> > Put your double-buffering screen behind another. Drag the frontmost
|> > screen down 20-30 rasterlines. Watch your double-buffering swap at
|> > an amazingly high rate.
|>
|> Yeah, I remember experiencing this nasty bug in my code, but it was
|> all my fault. It was due to a bad replyport assignment (I was assigning
|> the DispPorts to the ports intended to receive the SafeMessage). I
|> fixed this and it worked fine. Check that assignments in your code.
|>
|> BTW I'm writing some sample code: OpenDBScreen(), CloseDBScreen() and
|> ChangeDBScreen() (and one more function will probably be needed to
|> wait for the DispMessage). If anyone is interested (or if anyone

yeah that's something for my coder homepage! :)

|> has already written such a thing and I'm reinventing the wheel)
|> drop me a line.
|>
|> Greets,
|> --
|>  ---------------------------- --------------------------------------------
|> |       Jorge Acereda        |      Dream the same thing everynight       |
|> |   [e-mail]    |       I see our freedom in my sight        |
|> |       Intel Outside        |     No locked doors, no windows barred     |
|> |        Amiga Rules         |   No things to make my brain seem scarred  |
|>  ---------------------------- --------------------------------------------
------------------------------------------------------------------------
   [e-mail] (Juergen "Rally" Fischer)   =:)